-
Notifications
You must be signed in to change notification settings - Fork 102
Consolidate readmes and contribution guidelines #4281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
It duplicates the general readme
* [ ] I fill out the cherry-picking list in the PR template to the best of my abilities to signify which versions my update applies to. | ||
If unsure, I let reviewers know so that they can assist. | ||
|
||
## Foreman documentation minimalist style guide |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Potential reviewers: Note that all these style conventions have been moved from another document. I didn't write them and I'd like to avoid tweaking how they are worded 🙃 If anyone would like to see the wording improved, I'd suggest doing it in another PR. Thanks for understanding!
However, as noted in the PR description, I'd be happy to remove lines that are obsolete or redundant.
The PR preview for 8d63fbc is available at theforeman-foreman-documentation-preview-pr-4281.surge.sh No diff compared to the current base |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some comments, overall LGTM!
Co-authored-by: Maximilian Kolb <[email protected]>
cef0b72
to
8d63fbc
Compare
What changes are you introducing?
This PR looks at the existing readmes and contribution documents and attempts to make it easier to navigate through them. As a result, there are now:
One new thing that I'm adding is an explanation for the CP checklist in the PR template, to address #3219
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
To better separate types of information: readmes are for how to work with the repo; contributing is for how to contribute; style guide is for Foreman documentation conventions.
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
Hopefully the next step would be to review the style guide part to remove redundant information and duplicates. I found a few but I haven't really focused on that yet so if you spot something that could be dropped, I'd be happy to do so.
Contributor checklists
Please cherry-pick my commits into:
Review checklists
Tech review (performed by an Engineer who did not author the PR; can be skipped if tech review is unnecessary):
Style review (by a Technical Writer who did not author the PR):